Add serverless guidance for Feature Flags server SDKs#37110
Open
leoromanovsky wants to merge 7 commits into
Open
Add serverless guidance for Feature Flags server SDKs#37110leoromanovsky wants to merge 7 commits into
leoromanovsky wants to merge 7 commits into
Conversation
Contributor
Preview links (active after the
|
A-Rindone
reviewed
May 29, 2026
A-Rindone
approved these changes
May 29, 2026
Contributor
|
Opened DOCS-14576 to follow up with editorial review. |
aarsilv
approved these changes
May 29, 2026
- add link to Feature Flags API docs - add alert explaining EXPERIMENTAL_ env var
- add/update further reading links
Avoid commitments or predictions of future functionality, and only cover current capabilities in documentation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Feature Flags server SDK documentation did not explain how serverless workloads receive Remote Configuration payloads. Users running on AWS Lambda, Google Cloud Run, Azure Functions, and similar platforms need clear guidance that the Datadog Agent is required for server-side flag payload delivery, and that deeper serverless support is planned for a future release.
Changes
This PR adds a new Serverless Environments guide under the Feature Flags Implementation Patterns folder. The guide explains the Agent-backed Remote Configuration flow, the recommended stateful-Agent architecture for serverless workloads, the required environment variables, operational considerations, and validation steps.
It also adds environment-specific notes for AWS Lambda, Google Cloud Run services and functions, Azure Functions, AWS Fargate/container tasks, and managed edge/function platforms. The PR adds the Implementation Patterns folder to the Feature Flags left navigation and keeps the server SDK overview linked to the serverless guidance through both inline copy and further reading.
Decisions
The guidance stays high level and architecture-focused instead of duplicating language-specific SDK setup. The page explicitly calls out that the public Feature Flags API is for management, not per-request flag evaluation, and that application-owned defaults or static configuration are outside Remote Configuration delivery when no Agent path is available.
Validation performed locally:
git diff --checkyarn run build:hugoafter generating a transient Cdocs assets partial; the serverless page rendered before the folder move, but the full build exited on existing repo-wide missing generated data sources unrelated to this change.